Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1637

reference
374-tree-1
name
1637
tree-preservation-order

undefined

374-tpo-1
uprn
address-text
point
POINT (-1.030211 50.884457)
geometry
MULTIPOLYGON (((-1.030140 50.884449,-1.030143 50.884463,-1.030153 50.884476,-1.030169 50.884486,-1.030188 50.884493,-1.030210 50.884495,-1.030232 50.884493,-1.030252 50.884487,-1.030268 50.884477,-1.030278 50.884464,-1.030282 50.884451,-1.030279 50.884437,-1.030269 50.884424,-1.030254 50.884414,-1.030234 50.884407,-1.030212 50.884405,-1.030190 50.884407,-1.030170 50.884413,-1.030154 50.884423,-1.030144 50.884435,-1.030140 50.884449)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL